User distributed search results

ABSTRACT

A universal distributed search system allows users to find and distribute search results (possibly including advertisements) to those with whom they communicate. The search results can be easily distributed by the user via a simple interface that allows the search results to be easily added to the user&#39;s content. Search queries entered by the user or search results received from search components may be automatically refined by the system.

RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 119 based on U.S.Provisional Application Ser. No. 60/774,198, filed Feb. 17, 2006, thedisclosure of which is incorporated herein by reference. Thisapplication is also a continuation-in-part (CIP) under 37 C.F.R. §1.53(b) of application Ser. No. 10/366,466, filed Mar. 3, 2006, theentire contents of which are incorporated herein by reference.

BACKGROUND

A. Field of the Disclosure

The present disclosure relates generally to content creation, and morespecifically, to the enhancement of user created content with searchresults.

B. Description of the Related Art

In an increasingly networked world, users frequently use online sourcesto create and exchange information. Email, instant messaging (IM),message boards, websites, and blogs are all existing communicationtechnologies through which users can create and distribute content toother users. Frequently, in creating such content, a user may wish toreference other online information sources. For example, a userauthoring an email may use a browser to navigate to a web page that theuser would like to reference in the email, copy the link (e.g., theuniform resource locator (URL)) from the browser to a “clipboard,” andthen paste the link from the clipboard into the email. In this manner,the user can create an email message that contains links that areaccessible by an eventual reader of the email.

Search engines are a popular tool through which users enter a searchquery describing information of interest and receive back documents orlinks to documents that relate to the search query. Frequently, when“researching” content for an email message, IM message, message boardpost, website post, or blog post, the user may perform one or moresearches using one or more search engines to locate online documentsrelevant to the content. The user may then copy a link into the documentusing the above-described method of copying and pasting a link to thedocument. This process for annotating user created content can betedious, difficult to perform for average users, and often results intextual links in the final content that can be difficult to read.

Accordingly, it would be desirable to improve the above-describedcontent creation process.

SUMMARY

In one aspect, a content creation application includes a first interfaceconfigured to facilitate composition of a message by a user and a secondinterface configured to receive a search query. The content creationapplication additionally includes logic to automatically refine a searchquery. The content creation application additionally includes logic todisplay search results relating to the search query, and to receiveselections of the search results from the user, the content creationapplication automatically incorporating, in response to the selections,the selected ones of the search results into the message in the firstinterface.

In another aspect, a content creation application includes a firstinterface configured to facilitate composition of a message by a userand a second interface configured to receive a search query. The contentcreation application additionally includes logic to receive searchresults based on the search query; and logic to automatically refine thereceived search results. The content creation application additionallyincludes logic to display the refined search results, and to receiveselections of the refined search results from the user, the contentcreation application automatically incorporating, in response to theselections, the selected ones of the search results into the message inthe first interface.

In yet another aspect, a method includes providing an interfaceconfigured to facilitate composition of text by a user; receiving asearch query from the user; automatically refining the search query fromthe user; initiating a search based on the refined search query;receiving results of the search; displaying the results of the search inthe interface, the displayed results of the search each including aselection object; receiving selections of the selection objects from theuser; and associating the results of the search that correspond to theselected ones of the selection objects with the text in the interface.

In yet another aspect, a method includes providing an interfaceconfigured to facilitate composition of text by a user; receiving asearch query from the user; initiating a search based on the searchquery; receiving results of the search; automatically refining theresults of the search; displaying the results of the search in theinterface, the displayed results of the search each including aselection object; receiving selections of the selection objects from theuser; and associating the results of the search that correspond to theselected ones of the selection objects with the text in the interface.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate one or more embodiments of theinvention and, together with the description, explain the invention. Inthe drawings,

FIGS. 1A-1C are diagrams providing a conceptual overview of conceptsrelating to user distributed search results;

FIG. 2 is a diagram of an exemplary system in which concepts consistentwith the principles of the invention may be implemented;

FIG. 3 is an exemplary diagram of a client or server illustrated in FIG.2;

FIG. 4 is a flow chart illustrating exemplary operations consistent withuser distributed search;

FIG. 5 is a diagram of an exemplary email interface;

FIG. 6 is a diagram illustrating an exemplary email message that wasannotated to include a search result from a local search engine;

FIG. 7 is an exemplary interface illustrating application of userdistributed search to a message board environment;

FIG. 8 is an exemplary interface illustrating application of userdistributed search to an instant messaging conversation;

FIG. 9 is an exemplary interface illustrating application of userdistributed search to a blog authoring tool;

FIG. 10 is a diagram illustrating exemplary components in a userdistributed search system.

FIG. 11 is a flow chart illustrating additional exemplary operationsconsistent with user distributed search; and

FIG. 12 is an exemplary interface illustrating application of userdistributed search in which search results are automatically obtained;

FIG. 13 is a flow chart illustrating additional exemplary operationsconsistent with user distributed search;

FIG. 14 is an exemplary email interface illustrating refinement ofsearch queries; and

FIG. 15 is a flow chart illustrating additional exemplary operationsconsistent with user distributed search.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The detailed description does not limit the invention.

Overview

Implementations consistent with the principles of the invention relateto allowing users to distribute search results (possibly includingadvertisements) to those with whom they communicate. The search resultscan be easily distributed by the user via a simple interface that allowsthe search results to be added to the user's content with a single mouseclick (or other intuitive gestures or commands). In someimplementations, the search results may be automatically formatted whenbeing included into the user's content to create a high quality linkwithin the content.

FIGS. 1A-1C are diagrams providing a conceptual overview of conceptsdescribed herein. In this example, assume that a user (“Arthur”) isresponding to an email from a friend (“Mark”) requesting informationabout a camera lens. FIG. 1A is a diagram illustrating an exemplaryemail 110 in which Arthur responds with a short text message informingMark that the lens he was telling Mark about is the “100 mm F 2.8.”Email 110 exemplifies a typical user email responding to a question.FIG. 1B is a diagram illustrating an another exemplary email, labeled asemail 120, in which Arthur responds with the same message informing Markof the lens about which he was telling Mark. Additionally, in email 120,Arthur pastes a link 125 into email 120 that references a review of thelens. As can be seem by the text of link 125, link 125 is a textuallylong link that contains a number of terms that convey little informationand are probably meaningless to Mark. Email 120 exemplifies a anothertypical user email responding to a question.

FIG. 1C is a diagram illustrating an exemplary email 130 in which Arthurresponds to Mark's email using tools described herein. In contrast toemails 110 and 120, email 130 may include, in addition to the sametextual response 135 from Arthur to Mark, a number of links and/orcontent 140 that were inserted by Arthur when creating the email.Links/content 140 may be information that was automatically generated bythe email program used by Arthur in response to Arthur entering a searchquery such as “Canon 100 mm macro lens.” As shown, links/content 140include two images 141, two links 142 returned from a general web searchengine, an advertisement 143 returned from an advertisement searchengine, and a link 144 to a local company that was generated in responseto a search performed by a local search engine. Arthur may have chosento use each of links/content 140 by, for example, a single mouse clickon a graphical button associated with each of the results of the searchquery.

As can be appreciated from FIGS. 1A-1C, the workflow illustrated byemails 110 and 120 is sub-optimal for both the reader and the emailauthor. In contrast, email 130 (FIG. 1C) would likely be considered a“higher fidelity” communication than either email 110 or 120. Email 130includes a number of links to documents that are themselves easily readand that were explicitly selected by the author of the email.

System Overview

FIG. 2 is a diagram of an exemplary system 200 in which conceptsconsistent with the principles of the invention may be implemented.System 200 may include multiple clients 210 that can connect to servers,such as servers 220-A, 220-B or 230, via a network 240. Network 240 mayinclude a local area network (LAN), a wide area network (WAN), atelephone network, such as the Public Switched Telephone Network (PSTN),an intranet, the Internet, or a combination of networks. Two clients 210and three servers 220-A, 220-B and 230 are illustrated as connected tonetwork 240 for simplicity. In practice, there may be more clientsand/or servers. Also, in some instances, a client may perform one ormore functions of a server and a server may perform one or morefunctions of a client.

A client 210 may include a device, such as a personal computer, a laptop computer, a wireless telephone, a personal digital assistant (PDA),or another type of computation or communication device. Users of clients210 may access or receive information from servers 220-A, 220-B or 230.

Clients 210 may include software, such as a web browser 215, forinteracting with network 240. Browser programs are well known and arewidely available in the art. When browsers or browser programs arediscussed herein, these terms are intended to refer to any program thatallows a user to browse documents (e.g., web documents), regardless ofwhether the browser program is a stand alone program or an embeddedprogram, such as a browser program included as part of an operatingsystem.

Clients 210 may also include a local content creation component 218.Local content creation component 218 may include one or more softwareapplications designed to assist the user in generating content. Forexample, in the context of email, local content creation component 218may include an email application for composing, sending, and readingemail. In the context of instant messaging, local content creationcomponent 218 may include a client IM program for composing, sending,and reading instant messages. In alternate implementations, localcontent creation component 218 may be embodied as other content creationapplications, such as applications designed to assist users in creatingblog posts, designing or editing web sites, or posting to messageboards.

In some situations, users Of clients 210 may create content usingnetworked applications using server 230 in place of or as a supplementto using local content creation components 218. More particularly,server 230 may include content creation component 235, which may providecontent creation services to clients 210. For example, server 230 mayprovide email services to clients 210, such as by providing a webinterface through which users of clients 210 can compose, send, and reademail messages using browsers 215. In the context of instant messaging,content creation component 235 may be a server side portion of the IMapplication and may interact with a client-side IM application embodiedby local content creation component 218. In alternate implementations,content creation component 235 may be embodied as other network-basedcontent creation applications, such as applications designed to assistusers in creating blog posts, designing or editing web sites, or postingto message boards.

In the implementation shown, servers 220-A and 220-B may generallyprovide network services, such as search services, to clients 210 or toserver 230 via network service components 225-A and 225-B. For example,network service component 225-A may include a search engine designed toindex documents, such as web pages, connected to network 240. In thisimplementation, in response to search queries received from clients orother servers in system 200, network service component 225-A may returnlinks to documents determined by network service component 225-A to berelevant to the search query. Network service components 225, as well asbeing general web search engines, may be specialized web search engines,such as, for example, search engines that return general web searchresults, image search results, video search results, local searchresults, geographic search results, product search results, listingsearch results, email search results, blog search results, message groupsearch results, news search results, digitized content search results,local network search results (e.g. desktop search or corporate networksearch), or advertisements. The operation of search engines are known inthe art and will not be described further herein. Additionally, in someimplementations, the search results may include a history of previoussearch results viewed by the user. In other words, a user may select tosee a history of his/her search results.

In some implementations, one or more of network service components 225may provide advertisements. For example, assume that network servicecomponent 225-B of server 220-B is an advertisement server. Server 220-Bmay receive requests from other servers or from clients foradvertisements. The advertisements returned by server 220-B to therequesting server or client may be advertisements that are relevant to asearch query, document, or other data.

Although illustrated as single devices in FIG. 2, each of servers 220-A,220-B and 230 may be implemented as, for example, a single computingdevice or as multiple distributed computing devices. Also, in someimplementations, the functionality of multiple servers, such as servers220-B and 230, may be combined as a single server or a single group ofdistributed computing devices.

Exemplary Computing Device Architecture

FIG. 3 is an exemplary diagram of a computing device 300, such as one ofclients 210 or servers 220 or 230. Computing device 300 may include abus 310, a processor 320, a main memory 330, a read only memory (ROM)340, a storage device 350, an input device 360, an output device 370,and a communication interface 380. Bus 310 may include a path thatpermits communication among the components of computing device 300.

Processor 320 may include any type of processor, microprocessor, orprocessing logic that interprets and executes instructions. Main memory330 may include a random access memory (RAM) or another type of dynamicstorage device that may store information and instructions for executionby processor 320. ROM 340 may include a ROM device or another type ofstatic storage device that may store static information and instructionsfor use by processor 320. Storage device 350 may include a magneticand/or optical recording medium and its corresponding drive.

Input device 360 may include a mechanism that permits a user to inputinformation to computing device 300, such as a keyboard, a mouse, a pen,voice recognition and/or biometric mechanisms, etc. Output device 370may include a conventional mechanism that outputs information to theuser, including a display, a printer, a speaker, etc. Communicationinterface 380 may include any transceiver-like mechanism that enablescomputing device 300 to communicate with other devices and/or systems.For example, communication interface 380 may include mechanisms forcommunicating with another device or system via a network, such asnetwork 240.

Network service components 225 and content creation component 235 inservers 220-A, 220-B and 230, respectively, may be implemented insoftware and stored in a computer-readable medium, such as memory 330. Acomputer-readable medium may be defined as one or more physical orlogical memory devices and/or carrier waves.

The software instructions defining network service components 225 andcontent creation component 235 may be read into memory 330 from anothercomputer-readable medium, such as data storage device 350, or fromanother device via communication interface 380. The softwareinstructions contained in memory 330 cause processor 320 to performprocesses that will be described later. Alternatively, hardwiredcircuitry may be used in place of or in combination with softwareinstructions to implement processes consistent with the presentinvention. Thus, implementations consistent with the principles of theinvention are not limited to any specific combination of hardwarecircuitry and software.

User Distributed Search Results

Consistent with an aspect of the invention, users generating content,such as content created with one or both of content creation component235 or local content creation component 218, may easily incorporatesearch results and/or advertisements into their content creationworkflow. Incorporation of search results and/or advertisements in themanner described herein will be referred to as user distributed search(UDS).

FIG. 4 is a flow chart illustrating exemplary operations consistent withUDS. A user may begin by opening a content creation application for thetype of content that the user desires to create (act 401). For theexemplary operations shown in FIG. 4, assume that the user is composingan email using a web-based email application. That is, assume contentcreation component 235 provides web-based email services to the user viaa browser 215.

Content creation component 235 may provide a graphical interface thatincludes a UDS section (act 402). FIG. 5 is a diagram of an exemplaryemail interface 500. Email interface 500 may include fields such as“To:” field 502, “Subject:” field 504, and message field 506 in whichthe user may compose an email message in a typical manner. Additionally,in this implementation, interface 500 includes a UDS sidebar 510. Insome implementations, UDS sidebar 510 may be presented as a graphicalwindow, toolbar, or other element of interface 500 that the user canselectably display or hide from view. As shown, UDS sidebar 510 includesa search query field 520 and a number of search result sections 522-528.In this example, search result sections 522-528 include: image resultsection 522, local search result section 524, general web search resultsection 526, and advertisement result section 528. A selectablegraphical button, such as arrows 530 may allow the user to hide or vieweach of search result sections 522-528. As shown, results in localsearch result section 524 (“local results”) are hidden while searchresult sections 522, 526, and 528 are selected to show search results.In some implementations, the user of the email application may be ableto customize which of the search results sections are shown in UDSsidebar 510.

The user may, at some point while composing the email, enter a searchquery into search query field 520 (act 403). In some implementations,instead of the user manually entering a search, search queries may beautomatically generated and/or executed, such as by generating searchqueries based on content entered by the user, or semi-automaticallygenerated and/or executed, such as by allowing searches to be performedwhen a user “hovers” over a word or selection with a graphical pointingdevice (act 403). In response, content creation component 235 maytransmit the search query to each of the appropriate network servicecomponents 235. In this example, content creation component 235 maytransmit the search query to three network service components 235,respectively implementing an image search engine, a local web searchengine, and a general web search engine. Content creation component 235may also transmit the search query to another network search component235 that implements an advertisement server. The search results returnedfrom each of these four “search objects” may then be shown to the user(act 404). In some implementations, the user may select one of thesearch results to view the underlying document in a separate browserwindow.

As illustrated in the example of FIG. 5, the user entered the searchquery “Canon Macro Lens” into search query field 520. The returnedsearch results include a number of images 540 related to this search, anumber of relevant web sites 542 related to the search, and anadvertisement 544 related to the search. Each of the returned searchresults may include a link or other graphical selection object thatallows the user to select the search result for inclusion in to themessage being composed. In this implementation, a “save” link 550 isshown below each of the search results.

The user may decide to include one or more of the search results in theemail (act 405). The user may do so by simply selecting the appropriatesave link 550, which causes content creation component 235 to copy thecorresponding search result into the email. In response, contentcreation component 235 may write the selected results to the email, suchas to the message field 506 of the email (act 406). As shown, in thisexample, the user has selected two images 560, two general web results561, an advertisement 562, and a local search result 563, for inclusionin the email being composed. In one implementation, the results may beautomatically placed below message field 506 in the email. In otherimplementations, content creation component 235 may allow the user tocontrol the placement of the results in the email, such as bygraphically dragging different results to different positions in theemail. For example, a user may, by dragging a search result over animage or other portion of text, cause the image or other portion of textto become anchor text for the link that refers to the search results.Content creation component 235 may allow the user to implement othereditorial controls, such as providing the user with the ability toannotate search results or to add an indication of the search query thatwas used to generate the search result.

In some implementations, in addition to content creation component 235writing the selected results to the email, the content creationcomponent may additionally copy the selected results to other locations,such as an operating system's “clipboard.” Whether results are alsocopied to the clipboard may be a user selectable option, The user maythen, if desired, paste the results into other applications.

The user may continue to edit the content, enter or refine searchqueries, and select results for the content until the user is ready tosend or post the content (acts 407 and 408). In the example, of FIG. 5,the user may enter a “send email” command when the user is ready to sendthe email. The email, when received by the recipient, may appear asemail 130 (FIG. 1C). The recipient of the email may be able toconveniently view the web pages corresponding to the links by selectingthe links. The links underlying the image search results, in particular,may take the user to the web page at which the image is hosted.

As can be seen from FIG. 5, the selected results 560-563, in contrast tolinks that are typically pasted into emails between users, such as link125 (FIG. 1B), are formatted in a visually appealing manner and thusprovide a higher quality content than typical links that a user wouldnormally paste into content (e.g., such as link 125 of FIG. 1B). Morespecifically, the links relating to the search results may, as shown inFIGS. 1C and 5, include the actual link to the search result, a shortsnippet of text that may be selected based on terms in the search query,and the domain corresponding to the returned result. Additionally, theuser may select chosen results via a simple process, such as by a singlemouse click on a link 550 or by a “drag and drop” selection operationassociated with link 550, thus providing even relatively unsophisticatedcomputer users with the ability to enhance their content with searchresults.

FIG. 6 is a diagram illustrating an exemplary email message that wasannotated using UDS to include a search result to a local search engine.In this example, email message 600 is an email message relating to abook club meeting. The sender of the email message is informing theother members of the book club that the meeting location has changed toa local restaurant (“CaféDel Sol.”) To support this message, the senderhas added two search results from a local search engine. The first,result 602, refers to a web page that discusses the restaurant. Thesecond, result 604, links to a local search engine result web page 610that includes a map 615 showing the location of the restaurant. Asillustrated in this example, a user can quickly add links to valuableinformation to an email, such as a link to a map of a location referredto in the email. In some implementations, instead of a search resultbeing a link to a map, the search result may be a map image that is sentinline with the email message, another type of image, an address, aphone number, or a price of a product that is sent inline with the emailmessage.

Advertisements

In some implementations, content creators that place advertisement linksin their content may be given some form of credit if the reader of theadvertisement selects the advertisement link. The credit can be monetaryor take some other form. Because of the high likelihood that anadvertisement incorporated by a content creator into their content isrelevant and/or likely to be viewed by the reader, a number of differentbusiness models are possible. For example, advertisers may be charged apremium or charged based on a different rate scale for advertisementsdistributed via UDS.

Additional Exemplary Implementations of UDS

The above description of UDS was primarily in the context of sendingemail content. As previously mentioned, UDS can be applied equally wellto other forms of content creation. FIGS. 7-9 illustrate otheradditional applications of UDS.

FIG. 7 is an exemplary interface illustrating application of UDS to amessage board environment. A web message board can generally be definedas a facility on the web for holding discussions. Message boards aretypically organized into topics in which users post messages relating tothe appropriate topic.

In FIG. 7, an exemplary message board interface 700 is presented to auser, such as an interface presented through a browser 215. As shown ininterface 700, a first user has posted a message 710 asking for advicerelating to a crank for a bicycle. A second user responds with a message715. Through UDS, the poster supplements message 715 with a number ofsearch results 720. The search results 720 include images 725 of thecranks under discussion, an advertisement 730 for a bicycle storementioned in message 715, a link 735 to a web site of the company thatproduces the cranks, and a link 740 pointing to a local distributor ofthe cranks. Through UDS, the user responding to message 710 was able toeffectively supplement the text of message 715 with links that hespecifically selected as being relevant to the topic under discussion.

FIG. 8 is an exemplary interface illustrating application of UDS to aninstant messaging conversation. Instant messaging can generally bedefined as the act of instantly communicating between two or more peopleover a network such as the Internet.

In FIG. 8, an exemplary instant messaging interface 800 is presented toa user, such as an interface presented by a local content creationcomponent 218 (e.g., an IM client) executing at a client 210. Instantmessaging interface 800 includes a message display portion 810 throughwhich transmitted instant messages are displayed, a messaging area 820in which users may enter messages that they are going to transmit, andUDS interface 830. In this example, the two participants in theconversation (Mark and Cindy) are discussing possible vineyards tovisit. Through UDS, each user has selectively augmented their messageswith links relating to the particular vineyard under discussion. In thismanner, UDS interface 830 can enhance the quality of the instantmessaging conversation by, for example, allowing users to both searchfrom within IM interface 800 and easily share selected links from thesearch with other users.

FIG. 9 is an exemplary interface illustrating application of UDS to ablog authoring tool. A blog (shortened form of weblog or web log) is awebsite in which items are posted on a regular basis and generallydisplayed in reverse chronological order.

In FIG. 9, an exemplary interface 900 of a blog authoring tool presentedto a user, such as a web based blog authoring tool implemented bycontent creation component 235 or a locally executed blog authoring toolimplemented by local content creation component 218. Interface 900 mayinclude a blog authoring section 910 in which a blogger may enter andedit blog posts. UDS interface 920 allows the blogger to enter searchqueries and receive search results in a manner similar to UDS sidebar510 (FIG. 5). Search results selected by the blogger may be displayed inresult section 930 of interface 900. When the blogger is ready topublish the post, “publish post” button 940 may cause the text enteredby the blogger in section 910 and the search results selected by theblogger in result section 930 to both be published as a single blog postto the blogger's blog.

Additional Details of an Exemplary Implementation of the UDS

It can be recognized that the UDS described above can be implementedusing a number of different programming and hardware technologies. Ahigh-level description of one exemplary implementation will now begiven.

FIG. 10 is a diagram illustrating exemplary components in a UDS system.As shown in FIG. 10, a client 210 communicates with UDS engine 1037 atapplication server 230, which may in turn communicate with searchservices 1040-A through 1040-N at one or more servers 220. In thisimplementation, portions of the content application, such as an emailapplication, may be a web-based application that is transmitted tobrowser 215 on an on-demand basis. At browser 215, the email applicationmay include, for example, a JavaScript object 1016 that interfaces witha user interface portion 1017 to provide the final user interface thatis displayed in browser 215 based on, for example, HTML (hyper-textmarkup language) and CSS (cascading style sheets) data supplied fromJavaScript application 1016.

User interface portion 1017 and JavaScript object 1016 together act toreduce the start-stop start-stop nature of traditional browser-based webapplications, as JavaScript object 1016 adds a client-side layer thatcan handle many of the user interactions with user interface portion1017. Instead of loading a web page at the start of a user session,browser 215 may load JavaScript application 1016 from server 230 (or,alternatively, from a local cache). JavaScript object 1016 may beresponsible for both rendering the interface the user sees andcommunicating with content creation component of server 230 on theuser's behalf.

JavaScript object 1016 may be a dynamically configured object thatallows for dynamic selection of which network services, such as whichsearch services 1040, to use. JavaScript object 1016 may implement anumber of different functions at client 210. For example, JavaScriptobject 1016 may allow the interface to be positioned where desired inthe client display. Additionally, JavaScript object 1016 may implement asearch control object that limits search results to a small number ofhighly relevant results per search. The search control object mayannotate each search result with an element that, when clicked, allowsthe user to save the search result to the content creation interface.

In some implementations, JavaScript object 1016 may be an object that isdesigned to be easily integrated into existing web-based JavaScriptapplications, thus providing a convenient application programminginterface (API) through which programmers can incorporate UDS into theirprograms.

UDS engine 1037 may provide an interface with JavaScript object 1016. Inresponse to JavaScript object 1016, UDS interface may annotate searchrequests, perform searches through appropriate search services 1040-Athrough 1040-N, and serialize results of the searches. Search services1040-A through 1040-N may return search results, such as generalweb-based search results, image results, etc., or return relevantadvertisements, in response to requests from UDS engine 1037.

Automated Generation of Search Results

In the UDS described above, search results were primarily described asbeing obtained based on a search query entered by the user. In alternateimplementations, the UDS may automatically generate search queries andperform potential searches using automatically generated search queries.

Referring back to FIG. 4, in act 403, a search query may be entered by auser or automatically generated. FIG. 11 is a diagram illustratingadditional details that may be associated with act 403. In particular,as shown in FIG. 11, a search query may be generated based on a searchquery received from a user (act 1101) or based on the automaticgeneration of a search query (acts 1102-1104).

In act 1101, a search query may be received from a user. As previouslymentioned, this act may be based on a user typing a search query into asearch query field, such as search query field 520. Alternatively, Insome implementations, instead of the user typing a search query, theuser may select search terms in other ways, such as by “hovering” over aword or selection with a graphical pointing device

Instead of waiting for a user to provide a search query, the UDS mayautomatically generate search queries based on, for example, entityrecognition techniques performed using the content entered by the useror content otherwise associated with content creation application218/235 (act 1102). Entity recognition techniques are generally known inthe art, and may include, for example, techniques designed to recognizeentities such as products, places, organizations, or any other entitiesthat tend to be subjects of searches. The entity recognition techniquescan be based on linguistic grammar models or statistical models. In onepossible implementation, the entity recognition techniques may beparticularly adopted to locate terms that correspond to commercialproducts or terms that define an address, such as a postal address.

If an entity is recognized in act 1102 that is determined to be relevantenough for a search to be executed, the entity may be submitted as asearch query to the appropriate network service components 225 (acts1103 and 1104). In some implementations, if multiple entities arereceived they may be combined and submitted as a single search query,submitted as multiple separate search queries, or filtered to removeless relevant entities before combining the remaining entities as asearch query. In some implementations, the UDS system may only submitthe determined entity to certain ones of the network service components225 based on the type of entity. For example, an address may besubmitted to a mapping or local search network service component, whilea commercial product may be submitted to a shopping network servicecomponent and an advertisement network service component. Referring backto FIG. 4, the returned search results may then be shown in the UDSinterface and, as previously described, potentially selected by the userand incorporated into the content being created by the user (acts405-407).

In some implementations, the entity recognition techniques mayadditionally take into account context relating to the particularcontent creation component 218/235 or state of the content creationcomponent 218/235 that is being used by the user. For example, entityrecognition techniques applied to a message board content creationcomponent may be biased to look for terms in the content that relate tothe topic of the message board. As another example, entity recognitiontechniques applied to a blog authoring tool may be biased to look forterms in the content that relate to the general topic of the blog (e.g.,if the blog is a computer software blog, the entity recognitiontechniques may be biased to locate terms relating to computer software).

Acts 1102-1104 may be performed in real-time (or near real-time) as theuser is typing or otherwise editing content. In this way, potentiallyrelevant search results can be dynamically updated and shown to the userwithout interrupting the workflow of the user.

FIG. 12 is an exemplary interface 1200 illustrating application of userdistributed search in which search results are automatically obtained.Interface 1200 is an email interface that is similar to email interface500 (FIG. 5). In particular, interface 1200 may include “To:” field 502,“Subject:” field 504, and message field 506 in which the user maycompose an email message in a typical manner. Additionally, interface1200 may include selected search results 560 through 563, as describedpreviously.

In contrast to the example shown in FIG. 5, however, in which UDSsidebar 510 provides user-selectable search results, UDS sidebar 1210may include multiple sidebars, shown in interface 1200 as anauto-generated results section (sidebar) 1211 and a user-generatedresults section (sidebar) 1212. User-generated results section 1212 mayfunction similarly to UDS sidebar 510. That is, a user may enter searchqueries in search box 1220 and view results of the search in one or moresearch results sections 1222 and 1224.

Auto-generated results section 1211 may include search results that aregenerated automatically by the UDS (acts 1102-1104). The results may begenerated in-real time or in near real-time by the UDS system as theuser creates content (e.g., by typing content). Auto-generated resultssection 1211 may include a search query section 1240, in which thesearch query that was automatically generated by the UDS (act 1102) isshown, and a search result portion 1245, Search result portion 1245 mayinclude search results for the automatically generated query that isshown in search query section 1240. In this example, search resultportion 1245 includes an image result section 1246 and general websearch result section 1247. Graphical arrow buttons may allow the userto hide or view each of the search result sections. As shown, results inimage result section 1246 (“image results”) are hidden while general websearch result section 1247 is selected to show search results.

Whether auto-generated search results section 1211 and/or user-generatedsearch results section 1212 is displayed in interface 1200 may beconfigurable by the user. In the example of interface 1200, searchresults sections 1211 and 1212 include “close” buttons 1250 and 1251,respectively, which may operate to remove the respective resultssections 1211 or 1212 from the UDS interface. With these buttons, theuser may disable auto-generation of search queries.

Search results sections 1211 and 1212, in addition to being closeable bythe user, may include an option to allow the search results sections tobe detached from interface 1200. In other words, the user may be able tocause search results sections 1211 and 1212 to become a separate windowwithin a graphical interface.

In alternate implementations, instead of presenting an interface to theuser that includes multiple sidebars as shown in interface 1200, the UDSmay present a single sidebar to the user through which both manuallyentered search queries and automatically generated search queries areshown to the user. For example, the UDS system may automaticallygenerate search queries and display the results to the user as long asthe user does not manually enter a search query. When the user manuallyenters a search query, the system may refrain from automaticallygenerating further search queries. Also, the user may be able to disablethe automated portion of the search generation.

Further, in some alternate implementations, the UDS may automaticallygenerate search queries as described above but may not automaticallysubmit the search queries to network service components 325. Instead,the UDS may, for example, display the search queries in search querysection 1240, The user, if interested in the automatically generatedsearch query, may submit it to one or more of the network servicecomponents 225.

Refinement of UDS Search Results

With the UDS system described above, search results were presented tothe user based on a search query entered by the user or automaticallygenerated based on entity recognition techniques. In alternateimplementations, the search results or search queries may be furtherrefined by the UDS system before being shown to the user.

Referring back to FIG. 4, in act 403, a search query may be entered by auser or automatically generated. In response, content creation component235 may transmit the search query to each of the appropriate networkservice components 235 and the search results returned from each of thenetwork service components may then be shown to the user (act 404).

FIG. 13 is a flow chart illustrating additional exemplary operationsthat may be associated with act 404. The search query obtained in act403 may be refined by the UDS system (act 1302). In general, the UDS mayrefine the search query by modifying the search query with the goal ofincreasing the relevancy of the search results. Refining a search querydoes not necessarily imply that the search query is narrowed to returnfewer search results; in some situations, a refined search query mayreturn more search results than the original search query. In oneimplementation, the search query may be refined to include additionalinformation relating to the particular type of content creationapplication 218/235. For instance, if content creation application218/235 is an application designed to facilitate posts to a messageboard, content creation application 218/235 may automatically add termsto the search query that relate to the topic of the message board. Whena user is adding a post to the message board “rec.bicycles.tech,” forexample, the UDS system may modify user entered UDS search queries (orautomatically generated UDS search queries) to include terms relating tothe message board, such as by adding the terms “bicycle” or “gear,” etc.In some implementations, whether the UDS system adds terms to refine asearch query may be based on the specificity of the received searchquery. For example, if the received search query contains many terms orif it contains terms that are relatively uncommon, the UDS may refrainfrom additionally narrowing the search query, while a search query thatis determined by the UDS to be particularly broad may be refined.

In addition to refining search queries to include additional informationrelating to the particular type of content creation application 218/235,search queries may be refined based on particular users of the contentcreation application 218/235 or based on users to whom messages areaddressed that are created with content creation application 218/235(act 1302).

As an example of refining search queries based on the users of thecontent creation application 218/235 or based on users to whom messagesare addressed, consider the exemplary email message illustrated in FIG.14. In email message 1400, the sender of the email message is informingthe recipient of the email of a local restaurant (“Café Del Sol”) atwhich they are to meet. To support this message, the sender has addedsearch results 1460 from a local search engine that were selected fromlocal results 1445. In implementations consistent with aspects of theinvention, the search results may be based on search queries that wereautomatically refined to include references to the locations of thesender of the email message or the recipient of the email message. Forexample, local search result 1461 may link to a local search engineresult web page that includes a map showing the location of therestaurant relative to the location of the recipient of the emailmessage. The location of the email recipient may be known frominformation entered by the recipient when signing up for an emailaccount if the recipient of the email message is using the same emailplatform as the sender. As another example, local search results 1445may include search results based on multiple local searches, such as alocal search refined based on the sender's location and a local searchrefined based on the recipient's location.

As another example of refining search queries based on the users ofcontent creation application 218/235, the UDS system may generate anexplicit or implicit profile of the user and use the profile whenrefining the search results. The profile may be based on, for example,past searches by the user or explicit profile or preference informationentered by the user.

As yet another example of refining search queries, the UDS system mayrefine search queries by modifying individual terms within the searchqueries, such as by adding synonyms of terms already in the searchquery, by stemming terms already in the search query, or by substitutingor suggesting spelling corrections to terms in the search query.

The search query refined in act 1302 may be submitted to the appropriatenetwork service components (act 1303). The search results received backfrom the network search components may then be presented to the user(acts 1304 and 1305). Certain of these search results, such as searchresults 1445, for example, may be selected by the user and included inthe document, as previously described.

FIG. 15 is a flow chart illustrating additional exemplary operationsthat may be associated with act 404 consistent with an alternativeembodiment. The search query obtained in act 403 may be submitted to theappropriate network service components 225 by content creation component218/235 (act 1502). The search results may be received by contentcreation component 218/235 (act 1503). The received search results maybe refined by content creation component 218/235 by, for example,ranking the search results or filtering the search results (act 1504).This refinement may be performed with the goal of increasing therelevancy of the search results presented to the user. In general,refining search results will refer to modifying or reevaluating therelevance order of the search results. Typically, search results thatare higher in the relevance order are the results that are presented tothe user first or presented most prominently to the user.

In one implementation, additional information relating to the particulartype of content creation application 218/235 may be used to refine thesearch results. For instance, if content creation component 218/235 isan application designed to facilitate posts to a message board and theparticular message board being posted-to is the message board“rec.bicycles.tech,” content creation application 235 may refine thesearch results by ranking the results to emphasize results that are morerelevant to bicycles or removing (filtering) results that are notrelated to bicycles.

In another possible implementation, the search results may be refinedbased on information relating to the user of content creationapplication 218/235 or based on information relating to the intendedrecipients of the content. As an example of this, consider a profilecreated by or for the user that includes areas of interest of the user.The profile may be used as a basis to re-rank the search results. Inother possible implementations, other information, such as, for amessage board post, geographic information that is relevant to themessage board post, may be used to refine the search results.

The refined search results may then be presented to a user (act 1505).

Additional Concepts

The user selection of search results when creating content may providean indication that the selected search results are relevant to thesearch query. For example, the search results selected by a user may beused as part of a reputation network. In general, a reputation networkin some way quantifies the reputation or score of users as to theirexpertise in certain categories or topics. In the context of UDS, if aparticular user incorporates a large number of search results intocontent and the search results are frequently selected by readers of thecontent, this may be an indication that the user is an “expert” in thetopic relating to the content, and his reputation score for the topicmay be increased. This application may be particularly relevant tocontent applications such as message boards, where the message boardsare typically categorized by topic.

More generally, regarding reputation, the gesture of selecting a resultmay be feed back into the system to impact, for example, raw resultranking, raw value of an advertisement, raw reputation of a userperforming a selection, or raw reputation of an application using UDS.These raw reputation results can be used, for example, to modify adocument or advertisement ranking used by the underlying search engines.

Advertisements presented through UDS may, in particular, representadvertisements that have a higher likelihood of click through and maytherefore be more valuable to the advertiser. These advertisements may,for example, cost more than or be provided on different terms than otheradvertisements. In some implementations, the revenue or other benefitderived from advertisements selected by the content creator may be insome way shared with the content creator. In some situations, the factthat an advertisement is selected by an end user may be used in some wayto modify a reputation of the content creator that selected theadvertisement.

Additionally, in some implementations, content with search resultsselected by a user may be additionally automatically modified orsupplemented, such as by adding additional links to advertisements orproducts that are determined to be relevant to the selected searchresults. As an example of this, consider an advertisement for a merchantincluded in an email message by the author of the email message. It maybe desirable to include an additional advertisement from the merchant inthe email, such as an advertisement relating to an offer for freeshipping from the merchant. These additional or follow-on advertisementsmay be displayed within the message itself or as advertisementspresented to the user via a different channel. For example, if therecipient of the email message is viewing the email message using aweb-based email application, the follow-on advertisement may bedisplayed outside of the message itself, such as in a portion of thebrowser that the web-based email application normally uses to presentadvertisements to its users.

Additionally, in some implementations, the UDS search query field, suchas search query field 520 (FIG. 5), instead of causing searches to beexecuted through network service components (e.g., network searchengines), may perform other types of local or network search. Forexample, the search query may alternatively or additionally be submittedto a local (e.g., a desktop) search service or to a search serviceintegrated in the content creation application. For example, a networkemail content creation application may include a search service thatallows a user to search previously sent or received emails. In thissituation, the UDS search query field may additionally use the searchservices of the content creation application.

CONCLUSION

The foregoing description of exemplary embodiments of the inventionprovides illustration and description, but is not intended to beexhaustive or to limit the invention to the precise form disclosed.Modifications and variations are possible in light of the aboveteachings or may be acquired from practice of the invention.

Moreover, while series of acts have been described with regard to FIGS.4, 11, 13, and 15 the order of the acts may be varied in otherimplementations consistent with the invention. Moreover, non-dependentacts may be implemented in parallel.

It will also be apparent to one of ordinary skill in the art thataspects of the invention, as described above, may be implemented in manydifferent forms of software, firmware, and hardware in theimplementations illustrated in the figures. The actual software code orspecialized control hardware used to implement aspects consistent withthe principles of the invention is not limiting of the invention. Thus,the operation and behavior of the aspects of the invention weredescribed without reference to the specific software code—it beingunderstood that one of ordinary skill in the art would be able to designsoftware and control hardware to implement the aspects based on thedescription herein.

Further, certain portions of the invention may be implemented as “logic”or a “component” that performs one or more functions. This logic mayinclude hardware, such as an application specific integrated circuit ora field programmable gate array, software, or a combination of hardwareand software.

No element, act, or instruction used in the description of the inventionshould be construed as critical or essential to the invention unlessexplicitly described as such. Also, as used herein, the article “a” isintended to include one or more items. Where only one item is intended,the term “one” or similar language is used. Further, the phrase “basedon” is intended to mean “based, at least in part, on” unless explicitlystated otherwise.

1. A content creation application comprising: a first interfaceconfigured to facilitate composition of a message by a user; a secondinterface configured to receive a search query; logic to automaticallymodify the search query; and logic to display search results relating tothe modified search query, and to receive selections of the searchresults from the user, the content creation application automaticallyincorporating, in response to the selections, the selected ones of thesearch results into the message in the first interface.
 2. The contentcreation application of claim 1, wherein the logic to automaticallymodify the search query modifies the search query based on a type of thecontent creation application.
 3. The content creation application ofclaim 1, wherein the logic to automatically modify the search querymodifies the search query based on information relating to a user of thecontent creation application.
 4. The content creation application ofclaim 1, wherein the logic to automatically modify the search querymodifies the search query based on information relating to an intendedrecipient of the message being created by the user of the contentcreation application.
 5. The content creation application of claim 4,wherein the content creation application includes an email applicationor an instant messaging application.
 6. The content creation applicationof claim 1, wherein the logic to automatically modify the search querymodifies the search query by including synonyms or stems of terms in thesearch query, suggesting spelling corrections, or suggesting alternatequeries.
 7. The content creation application of claim 1, wherein thecontent creation application additionally comprises: logic to submit themodified search query to a network search component.
 8. The contentcreation application of claim 7, wherein the network search componentincludes a web search component, an image search component, a videosearch component, a local search component, a geographic searchcomponent, a product search component, a listing search component, anemail search component, a blog search component, a message group searchcomponent, a news search component, a digitized content searchcomponent, a desktop search component, or an advertisement searchcomponent.
 9. A content creation application comprising: a firstinterface configured to facilitate composition of a message by a user; asecond interface configured to receive a search query; logic to receivesearch results based on the search query; logic to automatically modifya relevance order of the received search results; and logic to displaythe search results according to the modified relevance order of thesearch results, and to receive selections of the displayed searchresults from the user, the content creation application automaticallyincorporating, in response to the selections, the selected ones of thesearch results into the message in the first interface.
 10. The contentcreation application of claim 9, wherein the logic to automaticallyrefine the received search results refines the received search resultsbased on a type of the content creation application.
 11. The contentcreation application of claim 9, wherein the logic to automaticallymodify a relevance order of the received search results modifies therelevance order of the search results based on information relating tothe user of the content creation application.
 12. The content creationapplication of claim 9, wherein the logic to automatically modify arelevance order of the received search results modifies the relevanceorder of the received search results based on information relating to anintended recipient of the message being created by the user of thecontent creation application.
 13. The content creation application ofclaim 12, wherein the content creation application includes an emailapplication or an instant messaging application.
 14. The contentcreation application of claim 9, wherein the logic to automaticallymodify a relevance order of the received search results modifies therelevance order by adjusting rankings of the received search results.15. The content creation application of claim 9, wherein the contentcreation application additionally comprises: logic to submit thegenerated search query to a network search component.
 16. The contentcreation application of claim 15, wherein the network search componentincludes a web search component, an image search component, a videosearch component, a local search component, a geographic searchcomponent, a product search component, a listing search component, anemail search component, a blog search component, a message group searchcomponent, a news search component, a digitized content searchcomponent, a desktop search component, or an advertisement searchcomponent.
 17. A method comprising: providing an interface configured tofacilitate composition of text by a user; receiving a search query fromthe user; automatically modifying the search query from the user;initiating a search based on the modified search query; receivingresults of the search; displaying the results of the search in theinterface, the displayed results of the search each including aselection object; receiving selections of the selection objects from theuser; and associating the results of the search that correspond to theselections of the selection objects with the text in the interface. 18.The method of claim 17, wherein automatically modifying the search queryincludes modifying the search query based on a type of a contentcreation application implemented by the interface.
 19. The method ofclaim 17, wherein automatically modifying the search query includesmodifying the search query based on information relating to the user.20. The method of claim 17, wherein automatically modifying the searchquery includes modifying the search query based on information relatingto an intended recipient of the text being created by the user.
 21. Themethod of claim 17, wherein initiating the search includes transmittingthe search query to a plurality of search services, the plurality ofsearch services returning one or more search result types.
 22. Themethod of claim 21, wherein the search result types include web searchresults, image search results, video search results, local searchresults, geographic search results, product search results, listingsearch results, email search results, blog search results, message groupsearch results, news search results, digitized content search results,desktop search results, or advertisements.
 23. The method of claim 17,wherein initiating the search includes transmitting the search query toa search component implemented locally at a computer of the user.
 24. Amethod comprising: providing an interface configured to facilitatecomposition of text by a user; receiving a search query from the user;initiating a search based on the search query; receiving results of thesearch; automatically modifying a relevance order of the results of thesearch; displaying the results of the search in the interface using themodified relevance order, the displayed results of the search eachincluding a selection object; receiving selections of the selectionobjects from the user; and associating the results of the search thatcorrespond to the selections of the selection objects with the text inthe interface.
 25. The method of claim 24, wherein automaticallymodifying a relevance order of the results of the search includesmodifying a relevance order of the results of the search based on a typeof a content creation application implemented by the interface.
 26. Themethod of claim 24, wherein automatically modifying a relevance order ofthe results of the search includes modifying the relevance order of theresults of the search based on information relating to the user.
 27. Themethod of claim 24, wherein automatically modifying a relevance order ofthe results of the search includes modifying the relevance order of theresults of the search based on information relating to an intendedrecipient of the text being created by the user.
 28. The method of claim24, wherein initiating the search includes transmitting the search queryto a plurality of search services, the plurality of search servicesreturning one or more search result types.